After the previous experiment with a town builder we came to the conclusion that we didn't really like it if you can place buildings wherever you want, in whatever rotation you want, without any sort of restriction.
It felt like it made it too easy to quickly plop down a bunch of buildings without putting too much thought into it.

So we gave it a second try but with everything on a grid!

Town Builder, Hex Grid Edition

We still wanted to experiment with things we had not done before, and thought a hexagonal grid might be a good fit for a town builder.

It has all of the restrictions of a grid but allows to build things in a slightly more organic looking way.

Something we haven't really touched on yet were the visual challenges for these prototypes. Both of them would require detailed, bespoke assets for buildings, resources, large amounts of land and of course the characters. Some of these we are familiar with, but others would have been a challenge for us to accomplish well.
You can see in the images we created some placeholder objects to represent buildings, and this was causing problems with scale. We weren't sure if we wanted to make these massive buildings, and thus the people would need to be tiny, or to stylize it and fudge the scales of different things.
We also had issues with art style, which would become a recurring problem for most of our prototypes except a few near the end of our experiments. While art style comes into play after a prototype a lot of the time, it can help inform a number of important decisions early on. It can be handy to have concept art or sketches to pull from, and we didn't have that for these. This leads into another problem of feeling engaged and passionate about an idea, and we weren't sure yet if we liked what we were doing, so a solid theme and setting never materialized.

In the end, due to game design issues as well as artistic issues, we decided not to move forward with this prototype either.

What we learned

• just adding a grid didn't really make the game interesting enough to inspire us to keep working on it.
  There have been enough town builders that work just like this and we were missing something unique that would make the game more interesting.
• we felt that in addition to gameplay we should think more about setting and art from the beginning as well
• committing to a multi-year big game project based on a tiny prototype is hard!

"Having an idea for a game is easy, but making the game is hard" is a phrase that I have heard many times from other game developers.
I don't think that's entirely true. For me, I find the "having an idea" part is hard as well - or at least having a good idea is.
Making a game can take many years. I want to work on games that excite myself, and that keep me excited for all these years. We're working on our games as a team, so everyone else needs to be excited to work on it too!
Also, you need to eventually sell the game, so it should be something that gets players excited as well! To do that it probably helps to be something somewhat unique that stands out from other games, maybe with a cool art style or a unique setting or some clever gameplay ideas.
Oh and it also helps to somewhat predict what the market is like when your game finally releases. Maybe everyone is super into deck builder farming games with puzzle mechanics now, but what about in a few years?

So, that's all a bit overwhelming, but you need to start somewhere, and we do that by building prototypes.
A prototype is a small, fairly unpolished slice of what could eventually become a game that is supposed to give you some ideas about what does and doesn't work. We only want to invest as much time into them as necessary.
It could be for testing many things, like the gameplay loop, or a single game mechanic, or a technical detail.

Once Parkitect 1.0 was released we started working on a few different prototypes in parallel to working on the Parkitect DLCs and multiplayer update.

They aren't pretty, but I thought it would be interesting to take a look at them!
Here's the first one, and we'll show others in future posts.

Town Builder

I really love games with lots of tiny people running around and doing their thing in the environment you've created for them.
I also enjoy working on games that have lots of simulations and systems interacting with each other in some way.

So naturally it made sense to give another management simulation game a try, and I thought a town builder would be a good idea - I've always wanted to make one and had prototyped 2-3 different ones before. They never got very far, but maybe this time things would work out :P

There was no clear idea for what the game would be, other than a town builder - so there was no setting or theme or gameplay mechanics. The goal of the prototype would be to figure out what we like and dislike in a town building game, and hopefully along the way it'd give us some inspiration for answering all these other questions.

It was pretty much a very basic version of Settlers III, with stacks of resources, buildings that create and request resources, and people running all over the place transporting the resources around.
Obviously it would have been fleshed out eventually to turn into something more unique, but the goal for this was to figure out whether this alone is interesting and fun, and what the technical challenges would be.
To learn some more new things that we didn't already know from Parkitect, there was no grid in this prototype, buildings could be placed and rotated freely however you wanted, and we wanted to have a large, smooth terrain.

What we learned

• distributing resources between buildings in a way that makes sense is quite challenging because there's so many things to consider! You don't want workers to walk from one end of the world to the other just to deliver something. Ideally a resource should get picked up by a worker who is fairly nearby, and get delivered somewhere that isn't crazy far away. At the same time though this could cause some buildings to never receive resources, which feels wrong. Also, maybe some buildings are more important than others because they produce something essential, so probably there also needs to be some priorities for that?
• having a large, relatively complex area to pathfind across seemed challenging but there are already some good solutions for it that work well (i.e. Navmeshes)
• simply plopping down buildings everywhere if you have unlimited space and can place them freely however you want is not very interesting. It gives a lot of freedom in how you design your town but if you always have room to squeeze in a building pretty much wherever you want it feels like you don't have to put a lot of thought into placement